Problem Note 31760: Cross Environment Data Access (CEDA) note might occur if you query SASHELP.VTABLE or use SAS Desktop Application in a DBCS version of SAS
During SAS installation, a post-processing step builds five indexed SAS data sets for the Desktop application. They are: DESKACT, DESKFD, DESKOBJ, FEEDDET, and FEEDER. For DBCS installations, this step produces Cross Environment Data Access (CEDA) notes in the SAS Log for each of the data sets. An example of the CEDA note follows:
NOTE: Data file SASHELP.FEEDER.DATA is in a format native to another host
or the file encoding does not match the session encoding. Cross Environment
Data Access will be used, which may require additional CPU resources and
reduce performance.
To remove the CEDA notes, you can use PROC COPY with the NOCLONE option on the selected data sets. For example:
proc copy in=sashelp out=new noclone memtype=data;
select deskact deskfd deskobj feeddet feeder;
run;
You can also use the DATA step with the ENCODING option:
data sashelp.deskact(encoding=sjis);
set sashelp.deskact;
run;
The five SAS data files with indexes are stored in "SASROOT/nls/en/sascfg"
on UNIX and in "!SASROOT\nls\1d\sascfg" on the PC.
Operating System and Release Information
SAS System | Base SAS | Tru64 UNIX | 9.1 TS1M0 | 9.3 TS1M0 |
OpenVMS Alpha | 9.1 TS1M0 | 9.3 TS1M0 |
Linux | 9.1 TS1M0 | 9.3 TS1M0 |
HP-UX IPF | 9.1 TS1M0 | 9.3 TS1M0 |
64-bit Enabled Solaris | 9.1 TS1M0 | 9.3 TS1M0 |
64-bit Enabled HP-UX | 9.1 TS1M0 | 9.3 TS1M0 |
64-bit Enabled AIX | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows XP Professional | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows NT Workstation | 9.1 TS1M0 | |
Microsoft Windows 2000 Professional | 9.1 TS1M0 | |
Microsoft Windows 2000 Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M0 | 9.3 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M0 | 9.3 TS1M0 |
z/OS | 9.1 TS1M0 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Use this short program to find out if these five data sets have incompatible encodings in your current SAS session. If so, you will see a note in the SAS Log like the following:
NOTE: Data file is in a format native to another host or the file encoding does not match the session encoding. Cross Environment Data Access will be used, which may require additional CPU resources and reduce performance.
data suname;
set sashelp.vtable(keep=libname memname modate datarep encoding);
if memname in( "DESKACT" "DESKFD" "DESKOBJ" "FEEDDET" "FEEDER");
run;
proc print data=suname;
run;
NOTE: Data file is in a format native to another host or the file encoding
does not match the session encoding. Cross Environment Data Access
will be used, which may require additional CPU resources and
reduce performance.
Obs libname memname modate datarep encoding
1 sashelp DESKACT 15MAY08:16:59:30 NATIVE wlatin1 Western (Windows)
2 sashelp DESKFD 15MAY08:16:59:30 NATIVE wlatin1 Western (Windows)
3 sashelp DESKOBJ 15MAY08:16:59:30 NATIVE wlatin1 Western (Windows)
4 sashelp FEEDDET 15MAY08:16:59:30 NATIVE wlatin1 Western (Windows)
5 sashelp FEEDER 15MAY08:16:59:30 NATIVE wlatin1 Western (Windows)
Five Western-encoded data sets built in a post-processing step during SAS installation will generate CEDA messages in SAS sessions with incompatible encodings.
Type: | Problem Note |
Priority: | low |
Date Modified: | 2008-05-19 09:29:02 |
Date Created: | 2008-04-10 21:03:09 |